Repository navigation
fix(kubescape): compare summary times at metadata precision - #5501
Conversation
Part of #5419. Preserve retained payloads while matching the creation-time precision used by metadata JSON.
Validation at
#5419 remains open. Signed image publication, a separately reviewed production image pin and fresh runtime acceptance are still required. |
@coderabbitai review |
✅ Action performed
|
|
No actionable comments were generated in the recent review.
|
Readiness rechecked at The exact-head regression and user evaluation in the validation receipt exercise retained fractional-second payloads, both storage codecs and the subsequent scanner update; payload bytes are preserved. Source review confirms identity and version guards remain in place. The required-gate helper confirms the check and workflow gates; the configured native code-quality rule remains API-unverifiable, with CLEAN and the protected queue retaining the provider decision. Promoting this publisher repair for protected integration. #5419 remains open: signed image publication, a separate immutable production pin, rollback/data safeguards and runtime acceptance are still required. |
Why
The scan-storage repair can reject unchanged records because two saved formats keep different timestamp precision, leaving reports inconsistent.
What
Compare creation times in the same saved format while preserving retained reports and all other identity checks. Publish the corrected repair for a separate reviewed rollout; production acceptance remains open.
Part of #5419